Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa23f8a734870d3ff0d65b2384c6b3b0035730b9553d24b7abce3dd3692db9d6

Tx prefix hash: c817e837136c543775748b0ec9ade6afbfa06b23c18cd559dff00c8d57d3ede6
Tx public key: 8a15a9da0a8f1e20cb8021721661d7afaba4d7781a91bf4e2a50ebfc8b46dc14
Timestamp: 1706378568 Timestamp [UCT]: 2024-01-27 18:02:48 Age [y:d:h:m:s]: 01:080:13:41:55
Block: 944604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318672 RingCT/type: yes/0
Extra: 018a15a9da0a8f1e20cb8021721661d7afaba4d7781a91bf4e2a50ebfc8b46dc1402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02830703657b38e3253881ececc543c7942e15c2df1ec90b0cde8d449adc3611 0.600000000000 1402886 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": 944614, "vin": [ { "gen": { "height": 944604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02830703657b38e3253881ececc543c7942e15c2df1ec90b0cde8d449adc3611" } } ], "extra": [ 1, 138, 21, 169, 218, 10, 143, 30, 32, 203, 128, 33, 114, 22, 97, 215, 175, 171, 164, 215, 120, 26, 145, 191, 78, 42, 80, 235, 252, 139, 70, 220, 20, 2, 17, 0, 0, 0, 3, 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