Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9fb4e89966a6782941ebe719a4f095379812722f8d45b5337a53b90022ab353

Tx prefix hash: 45fe9382497259ef62b3c68cb90cf494f9d4f583472df831a68e11a460f23934
Tx public key: e8efd963af346c402132be618ecdc9047435e1bccf2b34c522ad7784a77d5536
Timestamp: 1706695991 Timestamp [UCT]: 2024-01-31 10:13:11 Age [y:d:h:m:s]: 01:278:00:19:49
Block: 947239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457487 RingCT/type: yes/0
Extra: 01e8efd963af346c402132be618ecdc9047435e1bccf2b34c522ad7784a77d553602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20e5a42a4b7a5d6fb5441b1907e4d393e84e04054d0ef841ee4260e142a6f0aa 0.600000000000 1405587 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": 947249, "vin": [ { "gen": { "height": 947239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20e5a42a4b7a5d6fb5441b1907e4d393e84e04054d0ef841ee4260e142a6f0aa" } } ], "extra": [ 1, 232, 239, 217, 99, 175, 52, 108, 64, 33, 50, 190, 97, 142, 205, 201, 4, 116, 53, 225, 188, 207, 43, 52, 197, 34, 173, 119, 132, 167, 125, 85, 54, 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