Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e5bee79c4c790225a988786c1f5bf130ea74cebe32f9481df29d9893ac6a3bd

Tx prefix hash: 203492a641b7c0e2d50c8ff3efe1c5230d19bc01d208f5c25f874f648f33bbf1
Tx public key: cd81ed88f68a64fc15a9e5fb2d1d58f523d52a13638433447a2b9ef348afb66e
Timestamp: 1702369673 Timestamp [UCT]: 2023-12-12 08:27:53 Age [y:d:h:m:s]: 01:040:10:27:27
Block: 911399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290214 RingCT/type: yes/0
Extra: 01cd81ed88f68a64fc15a9e5fb2d1d58f523d52a13638433447a2b9ef348afb66e021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a566ea8bad213df66122b9a841b0528b1250146c40da8260418e72dcc9da3059 0.600000000000 1368601 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": 911409, "vin": [ { "gen": { "height": 911399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a566ea8bad213df66122b9a841b0528b1250146c40da8260418e72dcc9da3059" } } ], "extra": [ 1, 205, 129, 237, 136, 246, 138, 100, 252, 21, 169, 229, 251, 45, 29, 88, 245, 35, 213, 42, 19, 99, 132, 51, 68, 122, 43, 158, 243, 72, 175, 182, 110, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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