Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bd1a5bfa123dce6b65d989682c10e06473d8a8cdec5245cb5dac80b311b8cc0

Tx prefix hash: 66df5077073d28d0ee0a4777f9be819f029604eae5bb59ad78594a61d8930449
Tx public key: b5375a22db28282fd0a4630fdcf915730141b23c2f593c965fe3d98eee72e3ca
Timestamp: 1703106980 Timestamp [UCT]: 2023-12-20 21:16:20 Age [y:d:h:m:s]: 01:323:23:54:37
Block: 917525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490380 RingCT/type: yes/0
Extra: 01b5375a22db28282fd0a4630fdcf915730141b23c2f593c965fe3d98eee72e3ca021100000004bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adec49f39fe3742365fd2d8c7145e87275dfecdf2f0bcefc0657cdbd7a73d5a1 0.600000000000 1375107 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": 917535, "vin": [ { "gen": { "height": 917525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adec49f39fe3742365fd2d8c7145e87275dfecdf2f0bcefc0657cdbd7a73d5a1" } } ], "extra": [ 1, 181, 55, 90, 34, 219, 40, 40, 47, 208, 164, 99, 15, 220, 249, 21, 115, 1, 65, 178, 60, 47, 89, 60, 150, 95, 227, 217, 142, 238, 114, 227, 202, 2, 17, 0, 0, 0, 4, 191, 162, 34, 33, 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