Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f03a2b5e61925f15e3d5012d85271eee39bd19b40ad3a85c811f52c718b65c3

Tx prefix hash: b43b7e820b71050d19f3a2074e2dec3e316ee71bd2557d991f06e87379eca17a
Tx public key: 2338a31a8fd50575cf03bcfc01d9fcf51a23fa4297b9d1f23e6d7670f34822dc
Timestamp: 1711325456 Timestamp [UCT]: 2024-03-25 00:10:56 Age [y:d:h:m:s]: 01:021:18:02:10
Block: 985660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276503 RingCT/type: yes/0
Extra: 012338a31a8fd50575cf03bcfc01d9fcf51a23fa4297b9d1f23e6d7670f34822dc0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6eea9579889d2ca81a9d8f5e198cab93a60e7db6b5c1e610c01f73c73774a5b1 0.600000000000 1445877 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": 985670, "vin": [ { "gen": { "height": 985660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6eea9579889d2ca81a9d8f5e198cab93a60e7db6b5c1e610c01f73c73774a5b1" } } ], "extra": [ 1, 35, 56, 163, 26, 143, 213, 5, 117, 207, 3, 188, 252, 1, 217, 252, 245, 26, 35, 250, 66, 151, 185, 209, 242, 62, 109, 118, 112, 243, 72, 34, 220, 2, 17, 0, 0, 0, 3, 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