Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da87d34ae1c29c99570c9a748631d80b2945eecc0355431a2d0f1b3e890d8be6

Tx prefix hash: 57f0c826fdc02da1026d16e379f3b8fc16a476052628f99f3836b2e2b5d78e9f
Tx public key: 72be81d1152267614f02324200383abc40c94782d118070a21c018e8efa691b3
Timestamp: 1683579566 Timestamp [UCT]: 2023-05-08 20:59:26 Age [y:d:h:m:s]: 01:352:05:01:32
Block: 755867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512969 RingCT/type: yes/0
Extra: 0172be81d1152267614f02324200383abc40c94782d118070a21c018e8efa691b302110000000275e3f0e9000000000000000000

1 output(s) for total of 1.920874752000 dcy

stealth address amount amount idx
00: 0bb0c6e67e844823b4714f8f17d744f3028b755c7107d27c74cee4aacd56e521 1.920874752000 1204206 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": 755877, "vin": [ { "gen": { "height": 755867 } } ], "vout": [ { "amount": 1920874752, "target": { "key": "0bb0c6e67e844823b4714f8f17d744f3028b755c7107d27c74cee4aacd56e521" } } ], "extra": [ 1, 114, 190, 129, 209, 21, 34, 103, 97, 79, 2, 50, 66, 0, 56, 58, 188, 64, 201, 71, 130, 209, 24, 7, 10, 33, 192, 24, 232, 239, 166, 145, 179, 2, 17, 0, 0, 0, 2, 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