Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 961287641153fb8fa29052ed62fa60d448fc08b4da4b20ac47a793dbd1f06f9d

Tx prefix hash: bc8bde2779bcdd45f225820d5979749c0d245e54e58fc9a6b7b24abfddc9d471
Tx public key: e476a89595e34dc669059c8d39717e64f8b21cfb2c7b757dfda0c213855c7617
Timestamp: 1709804157 Timestamp [UCT]: 2024-03-07 09:35:57 Age [y:d:h:m:s]: 01:241:20:04:38
Block: 973036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431545 RingCT/type: yes/0
Extra: 01e476a89595e34dc669059c8d39717e64f8b21cfb2c7b757dfda0c213855c761702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33aaa04e6e8576c699f52621215e1ff847c8ff9c43bf92bc3ceead8e694f7d5b 0.600000000000 1432967 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": 973046, "vin": [ { "gen": { "height": 973036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33aaa04e6e8576c699f52621215e1ff847c8ff9c43bf92bc3ceead8e694f7d5b" } } ], "extra": [ 1, 228, 118, 168, 149, 149, 227, 77, 198, 105, 5, 156, 141, 57, 113, 126, 100, 248, 178, 28, 251, 44, 123, 117, 125, 253, 160, 194, 19, 133, 92, 118, 23, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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