Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91621ec38d56a0851d7a456063db59f1540c07ce42aab8a7063ca13aa40fb1d9

Tx prefix hash: 7c5aaa755a78caf8d5a3c736427e91e07c3bfc8c47f4131b2831f731a5364e31
Tx public key: 370460e60ba9cffcd72521540e70e26f50a25bd5df5b3e431cfdc7294c284ded
Timestamp: 1724117497 Timestamp [UCT]: 2024-08-20 01:31:37 Age [y:d:h:m:s]: 00:294:05:10:32
Block: 1091696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210190 RingCT/type: yes/0
Extra: 01370460e60ba9cffcd72521540e70e26f50a25bd5df5b3e431cfdc7294c284ded02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9377fe94f6c949dac47d6e93056a07dd1e4085d2eec892d6b5e0de1b82d966aa 0.600000000000 1566329 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": 1091706, "vin": [ { "gen": { "height": 1091696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9377fe94f6c949dac47d6e93056a07dd1e4085d2eec892d6b5e0de1b82d966aa" } } ], "extra": [ 1, 55, 4, 96, 230, 11, 169, 207, 252, 215, 37, 33, 84, 14, 112, 226, 111, 80, 162, 91, 213, 223, 91, 62, 67, 28, 253, 199, 41, 76, 40, 77, 237, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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