Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c9aefd1a66afa55d146db251cf8202b51d8f13f8d81e12139695fafff8b706

Tx prefix hash: b5b57180cfbcb0de0a2fb66123986787592661cd0bc9251994f6b207453e8dd2
Tx public key: 5e07585b7d84815344141c9c420f80607ad617e6a8d4af3842eb7c7ecc389e48
Timestamp: 1710393566 Timestamp [UCT]: 2024-03-14 05:19:26 Age [y:d:h:m:s]: 00:346:02:03:33
Block: 977934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247402 RingCT/type: yes/0
Extra: 015e07585b7d84815344141c9c420f80607ad617e6a8d4af3842eb7c7ecc389e4802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fdd973fc924a6e23c0c3b3d36e517de74aa3ef3fc0cfa9d94a9db9420b53035 0.600000000000 1437943 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": 977944, "vin": [ { "gen": { "height": 977934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fdd973fc924a6e23c0c3b3d36e517de74aa3ef3fc0cfa9d94a9db9420b53035" } } ], "extra": [ 1, 94, 7, 88, 91, 125, 132, 129, 83, 68, 20, 28, 156, 66, 15, 128, 96, 122, 214, 23, 230, 168, 212, 175, 56, 66, 235, 124, 126, 204, 56, 158, 72, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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