Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070cf6266accab3e1ad476a51f57532a1be074314d53361bf4df96703f519f4b

Tx prefix hash: 01c911269dfec3f8e59352141dea21c28d31d2dc8e4083eab7312d24609cd45b
Tx public key: af4e15ade5035fac4c6be5f8dbc5ae7334f54a87c0243dd40a366c0100b52be5
Timestamp: 1706925513 Timestamp [UCT]: 2024-02-03 01:58:33 Age [y:d:h:m:s]: 01:307:16:14:50
Block: 949146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478720 RingCT/type: yes/0
Extra: 01af4e15ade5035fac4c6be5f8dbc5ae7334f54a87c0243dd40a366c0100b52be502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e3c9b9c4789376e7d2806c38c2fd7d9984c5465802c289dd4f6bca0e91ec90 0.600000000000 1407668 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": 949156, "vin": [ { "gen": { "height": 949146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e3c9b9c4789376e7d2806c38c2fd7d9984c5465802c289dd4f6bca0e91ec90" } } ], "extra": [ 1, 175, 78, 21, 173, 229, 3, 95, 172, 76, 107, 229, 248, 219, 197, 174, 115, 52, 245, 74, 135, 192, 36, 61, 212, 10, 54, 108, 1, 0, 181, 43, 229, 2, 17, 0, 0, 0, 4, 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