Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb4070857640c6aba937d5d6c5510f80ec1cdf372fbbcf1725279bf90207bc62

Tx prefix hash: b8c1245a44c7e3cfa557cc7b75ac887f38794bef4a709bb46d715abd4dcc9493
Tx public key: 478373eeefbcf5f0da6044acaf2ddd6b2f3c1a8d99ef079eecd2a60f5033143d
Timestamp: 1577913299 Timestamp [UCT]: 2020-01-01 21:14:59 Age [y:d:h:m:s]: 05:166:15:39:41
Block: 36626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1268915 RingCT/type: yes/0
Extra: 01478373eeefbcf5f0da6044acaf2ddd6b2f3c1a8d99ef079eecd2a60f5033143d0211000000264ac5aa02000000000000000000

1 output(s) for total of 464.134349149000 dcy

stealth address amount amount idx
00: b6de0be7a25665073918e17913886711ff1116f758b56aebf0c8d31888b74745 464.134349149000 62090 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": 36636, "vin": [ { "gen": { "height": 36626 } } ], "vout": [ { "amount": 464134349149, "target": { "key": "b6de0be7a25665073918e17913886711ff1116f758b56aebf0c8d31888b74745" } } ], "extra": [ 1, 71, 131, 115, 238, 239, 188, 245, 240, 218, 96, 68, 172, 175, 45, 221, 107, 47, 60, 26, 141, 153, 239, 7, 158, 236, 210, 166, 15, 80, 51, 20, 61, 2, 17, 0, 0, 0, 38, 74, 197, 170, 2, 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