Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 740bde5a02c67a7ffa83cf6194567f4beea2192cc01838b83608cb2d3c609b89

Tx prefix hash: 544ecb1c089b17627ae59bab5bc57a9ac186b3e9bd737ad66b4f33f2ef84c067
Tx public key: 72beeadd75085e1efafc9f5c824374173fd5b0bc6661209c66b7d4a3545ccf7b
Timestamp: 1706477381 Timestamp [UCT]: 2024-01-28 21:29:41 Age [y:d:h:m:s]: 00:237:01:18:27
Block: 945422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169828 RingCT/type: yes/0
Extra: 0172beeadd75085e1efafc9f5c824374173fd5b0bc6661209c66b7d4a3545ccf7b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bb066405ce8bd8e413e8e3f53cae35a45d4fe3ea869e8aab03479a169fab459 0.600000000000 1403736 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": 945432, "vin": [ { "gen": { "height": 945422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bb066405ce8bd8e413e8e3f53cae35a45d4fe3ea869e8aab03479a169fab459" } } ], "extra": [ 1, 114, 190, 234, 221, 117, 8, 94, 30, 250, 252, 159, 92, 130, 67, 116, 23, 63, 213, 176, 188, 102, 97, 32, 156, 102, 183, 212, 163, 84, 92, 207, 123, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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