Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe37fbbfe581e6f5541b086a0a326f08bc269899f280d1634819452bdc71abe

Tx prefix hash: 2bccacda9f53708043ff65c1b66f94626ed101cf558e042042bbabc50f61617e
Tx public key: 36f2b0eecb80dbf5f81e97845883973f2ae21515ec3b58e896f6bbdc18fa25b4
Timestamp: 1701666272 Timestamp [UCT]: 2023-12-04 05:04:32 Age [y:d:h:m:s]: 01:350:22:07:05
Block: 905548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509701 RingCT/type: yes/0
Extra: 0136f2b0eecb80dbf5f81e97845883973f2ae21515ec3b58e896f6bbdc18fa25b402110000000733af99f4000000000000000000

1 output(s) for total of 0.613117258000 dcy

stealth address amount amount idx
00: 8d6b136ba0671a48f15ee30e1c56cc42474ce687a91310b2be4de62ce508c9bd 0.613117258000 1362437 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": 905558, "vin": [ { "gen": { "height": 905548 } } ], "vout": [ { "amount": 613117258, "target": { "key": "8d6b136ba0671a48f15ee30e1c56cc42474ce687a91310b2be4de62ce508c9bd" } } ], "extra": [ 1, 54, 242, 176, 238, 203, 128, 219, 245, 248, 30, 151, 132, 88, 131, 151, 63, 42, 226, 21, 21, 236, 59, 88, 232, 150, 246, 187, 220, 24, 250, 37, 180, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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