Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547b09f94575260a5d4235d8c9daeef49deaac268f824f3fb50c971e1583c22f

Tx prefix hash: 070f69c98a4fe7a771094a19fd166af010d003928890625cb725f65a7e49dba5
Tx public key: 351d3df9ef49cc4100e64cf1198b249fb0a832ba01935a0c5dfb5c1188c0c5ae
Timestamp: 1710832851 Timestamp [UCT]: 2024-03-19 07:20:51 Age [y:d:h:m:s]: 00:361:16:02:56
Block: 981572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258604 RingCT/type: yes/0
Extra: 01351d3df9ef49cc4100e64cf1198b249fb0a832ba01935a0c5dfb5c1188c0c5ae0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a68cd55ba1423e1665c840d520d46bf5bfce7042bafb78b4e43ea7a6bf5b36f2 0.600000000000 1441669 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": 981582, "vin": [ { "gen": { "height": 981572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a68cd55ba1423e1665c840d520d46bf5bfce7042bafb78b4e43ea7a6bf5b36f2" } } ], "extra": [ 1, 53, 29, 61, 249, 239, 73, 204, 65, 0, 230, 76, 241, 25, 139, 36, 159, 176, 168, 50, 186, 1, 147, 90, 12, 93, 251, 92, 17, 136, 192, 197, 174, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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