Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4d9e54698868426d346f6bbb7a48dd392443d060e7c18ff14e3bf85714cb3d7

Tx prefix hash: 9d9d8595d989829591d5ad242f9ffbcfda3efb594560d12287d39a7ce97557b7
Tx public key: e16cec7269e92ee4d67d50378aa1a6a56bb8c8963294063980493e2a76b8f3aa
Timestamp: 1704379084 Timestamp [UCT]: 2024-01-04 14:38:04 Age [y:d:h:m:s]: 01:304:03:06:16
Block: 928051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476170 RingCT/type: yes/0
Extra: 01e16cec7269e92ee4d67d50378aa1a6a56bb8c8963294063980493e2a76b8f3aa02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9937f59a441aa9a57612c363606e841ff78a0f701ef2666b44fa339ce1f6e7f 0.600000000000 1385907 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": 928061, "vin": [ { "gen": { "height": 928051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9937f59a441aa9a57612c363606e841ff78a0f701ef2666b44fa339ce1f6e7f" } } ], "extra": [ 1, 225, 108, 236, 114, 105, 233, 46, 228, 214, 125, 80, 55, 138, 161, 166, 165, 107, 184, 200, 150, 50, 148, 6, 57, 128, 73, 62, 42, 118, 184, 243, 170, 2, 17, 0, 0, 0, 2, 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