Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 998ffd9cd019baf8229d86a3d4d3603a93c94d5349edcc953e9d2594fbc72124

Tx prefix hash: df3e85214ad4b2d1f5ac357cdbc80d08b90f1e4299ae9c0f7a348b8d3980cf12
Tx public key: 603c3688c3bbc1c773cbaaa87c00718137335f47381f6d631f3193ad115c01e4
Timestamp: 1701935387 Timestamp [UCT]: 2023-12-07 07:49:47 Age [y:d:h:m:s]: 01:333:22:54:22
Block: 907788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497533 RingCT/type: yes/0
Extra: 01603c3688c3bbc1c773cbaaa87c00718137335f47381f6d631f3193ad115c01e40211000000014b8f5122000000000000000000

1 output(s) for total of 0.602728167000 dcy

stealth address amount amount idx
00: ce6fbe223eb51b6aa25a665889d4f893a3ceec9559c1cf28c0c8b7642b665ddb 0.602728167000 1364781 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": 907798, "vin": [ { "gen": { "height": 907788 } } ], "vout": [ { "amount": 602728167, "target": { "key": "ce6fbe223eb51b6aa25a665889d4f893a3ceec9559c1cf28c0c8b7642b665ddb" } } ], "extra": [ 1, 96, 60, 54, 136, 195, 187, 193, 199, 115, 203, 170, 168, 124, 0, 113, 129, 55, 51, 95, 71, 56, 31, 109, 99, 31, 49, 147, 173, 17, 92, 1, 228, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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