Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bb0d0ce27958740260f69beb57abaa20394bf6e18e454b9c70cecd208b96f9a4

Tx prefix hash: c9317a3b686fa388b6a25626f04964048336d723f49d2a4cf79f95e9077ac766
Tx public key: db4c20e2025e6e2a365ffa4171b704bf218cbf8105225f925c2db29e63d5ccb1
Timestamp: 1669221354 Timestamp [UCT]: 2022-11-23 16:35:54 Age [y:d:h:m:s]: 02:350:15:21:46
Block: 637469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 770046 RingCT/type: yes/0
Extra: 01db4c20e2025e6e2a365ffa4171b704bf218cbf8105225f925c2db29e63d5ccb1021100000001e6d27f9c000000000000000000

1 output(s) for total of 4.740242742000 dcy

stealth address amount amount idx
00: 126def5940151f7b37113757a97ec82fd4382c917fdea482b3fb4e7ca93f6a96 4.740242742000 1077026 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 637479, "vin": [ { "gen": { "height": 637469 } } ], "vout": [ { "amount": 4740242742, "target": { "key": "126def5940151f7b37113757a97ec82fd4382c917fdea482b3fb4e7ca93f6a96" } } ], "extra": [ 1, 219, 76, 32, 226, 2, 94, 110, 42, 54, 95, 250, 65, 113, 183, 4, 191, 33, 140, 191, 129, 5, 34, 95, 146, 92, 45, 178, 158, 99, 213, 204, 177, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8