Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 370e8f4bfa38a1f138dc087c358a6a96c9af303b2fe3aa6458501699c93f3bf9

Tx prefix hash: 334d95ffeb2574c8ebbaa23c5cb5363c3d862c18fe2858ff8c697de867a394f0
Tx public key: d7d4b16a31bd238307d43e11fa77340d4ea118ab69fcec05f2aa8d4e6dc69d1a
Timestamp: 1725650530 Timestamp [UCT]: 2024-09-06 19:22:10 Age [y:d:h:m:s]: 00:189:17:52:00
Block: 1104403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135454 RingCT/type: yes/0
Extra: 01d7d4b16a31bd238307d43e11fa77340d4ea118ab69fcec05f2aa8d4e6dc69d1a02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a67e417ee03dfbfe0d25d76b6f60cf495f63f2ba3af9b274aa7085a1f7697e3 0.600000000000 1581532 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": 1104413, "vin": [ { "gen": { "height": 1104403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a67e417ee03dfbfe0d25d76b6f60cf495f63f2ba3af9b274aa7085a1f7697e3" } } ], "extra": [ 1, 215, 212, 177, 106, 49, 189, 35, 131, 7, 212, 62, 17, 250, 119, 52, 13, 78, 161, 24, 171, 105, 252, 236, 5, 242, 170, 141, 78, 109, 198, 157, 26, 2, 17, 0, 0, 0, 13, 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