Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd89fa3da1f07ce7ee5a51d7c1f6e1f5f92bcd61069007528a57142cbfa39129

Tx prefix hash: 41122049b85411217a1f05cb9e2948bd611556298fb38e16ae2df60600a8aea4
Tx public key: f6503f75171c1a811b21ce9e82ec6733f89d5da0f2bfd4b592e5fb6e89032cbf
Timestamp: 1720460658 Timestamp [UCT]: 2024-07-08 17:44:18 Age [y:d:h:m:s]: 01:123:22:02:33
Block: 1061379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347082 RingCT/type: yes/0
Extra: 01f6503f75171c1a811b21ce9e82ec6733f89d5da0f2bfd4b592e5fb6e89032cbf021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf9b8d1a59361a8972cc08c241c3dd0b4d114b7f53640a978e90f7d32e6b0a59 0.600000000000 1531870 of 15

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": 1061389, "vin": [ { "gen": { "height": 1061379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf9b8d1a59361a8972cc08c241c3dd0b4d114b7f53640a978e90f7d32e6b0a59" } } ], "extra": [ 1, 246, 80, 63, 117, 23, 28, 26, 129, 27, 33, 206, 158, 130, 236, 103, 51, 248, 157, 93, 160, 242, 191, 212, 181, 146, 229, 251, 110, 137, 3, 44, 191, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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