Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b371930d9ecaa26f7e0d9b279e2bd4adfb103023f64436b26d4016f7f716b039

Tx prefix hash: a685d373d667b4fc0838336ae163ea49b5b8b18d0f50422ccdee208ebeeb50ba
Tx public key: a3a503f19c10ea4352c1bbaed2b44afbb3e84d6070ad3d286150d007934d35aa
Timestamp: 1736926880 Timestamp [UCT]: 2025-01-15 07:41:20 Age [y:d:h:m:s]: 00:339:23:19:36
Block: 1197735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240542 RingCT/type: yes/0
Extra: 01a3a503f19c10ea4352c1bbaed2b44afbb3e84d6070ad3d286150d007934d35aa02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a04b15aa158652c9a19a533c31da3271a2e2d3d2e1522738f610559e8854770c 0.600000000000 1684350 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": 1197745, "vin": [ { "gen": { "height": 1197735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a04b15aa158652c9a19a533c31da3271a2e2d3d2e1522738f610559e8854770c" } } ], "extra": [ 1, 163, 165, 3, 241, 156, 16, 234, 67, 82, 193, 187, 174, 210, 180, 74, 251, 179, 232, 77, 96, 112, 173, 61, 40, 97, 80, 208, 7, 147, 77, 53, 170, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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