Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ecfe5a4dfb6e4ba4da09ca5d706c9240a662949c6cd8d0be3e67449516c13c0

Tx prefix hash: 1db4ffae1bdc55d82fb37fb69b6adec28c21ee8fa2afc43ed664cae06068c1d0
Tx public key: 13be3123de12c0edab098e3a8ba77a0791b68343dc4b86ece6e40a388b64838e
Timestamp: 1631667876 Timestamp [UCT]: 2021-09-15 01:04:36 Age [y:d:h:m:s]: 03:112:00:19:02
Block: 333989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 855702 RingCT/type: yes/0
Extra: 0113be3123de12c0edab098e3a8ba77a0791b68343dc4b86ece6e40a388b64838e0211000000023fc41461000000000000000000

1 output(s) for total of 48.012712051000 dcy

stealth address amount amount idx
00: f2081588e9e906109baea06c32371efc4bca47d30a8fe90048449496d91e3ec2 48.012712051000 689036 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": 333999, "vin": [ { "gen": { "height": 333989 } } ], "vout": [ { "amount": 48012712051, "target": { "key": "f2081588e9e906109baea06c32371efc4bca47d30a8fe90048449496d91e3ec2" } } ], "extra": [ 1, 19, 190, 49, 35, 222, 18, 192, 237, 171, 9, 142, 58, 139, 167, 122, 7, 145, 182, 131, 67, 220, 75, 134, 236, 230, 228, 10, 56, 139, 100, 131, 142, 2, 17, 0, 0, 0, 2, 63, 196, 20, 97, 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