Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4b5bb1fd91d9aafb6a96f66acb974d67e9bda24fac0ccb7e6a9b67094db9b5

Tx prefix hash: cd0a5750f2106c3632b12e12eec9a122cb9b362d9d08c0db5e2cb20c6fe332ce
Tx public key: 5770f80309428906067cf3a9747d40106227e7f1fc349460dbdc7bc3e1307a82
Timestamp: 1652864446 Timestamp [UCT]: 2022-05-18 09:00:46 Age [y:d:h:m:s]: 03:166:21:27:41
Block: 503483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 898270 RingCT/type: yes/0
Extra: 015770f80309428906067cf3a9747d40106227e7f1fc349460dbdc7bc3e1307a8202110000000675e3f0e9000000000000000000

1 output(s) for total of 13.176002223000 dcy

stealth address amount amount idx
00: a64c0218314ba853178eccb675fb3f82304fe45b11b9ac026141edcc6142eec2 13.176002223000 928558 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": 503493, "vin": [ { "gen": { "height": 503483 } } ], "vout": [ { "amount": 13176002223, "target": { "key": "a64c0218314ba853178eccb675fb3f82304fe45b11b9ac026141edcc6142eec2" } } ], "extra": [ 1, 87, 112, 248, 3, 9, 66, 137, 6, 6, 124, 243, 169, 116, 125, 64, 16, 98, 39, 231, 241, 252, 52, 148, 96, 219, 220, 123, 195, 225, 48, 122, 130, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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