Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a05ebe3a1271fecf190915351a7103dc14bea0a5f4919a304d65359fa3b363d

Tx prefix hash: e41d0d73810964441edd7f043dc31e1b03372684aeeae2d60843d3b76b04ad59
Tx public key: 5ad27faea8fae87fc82246f24ca1e97a0d9572857b063f0931405a7abb4b478b
Timestamp: 1710201854 Timestamp [UCT]: 2024-03-12 00:04:14 Age [y:d:h:m:s]: 01:036:06:00:19
Block: 976336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286897 RingCT/type: yes/0
Extra: 015ad27faea8fae87fc82246f24ca1e97a0d9572857b063f0931405a7abb4b478b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa33fc1bcc0fd0ec1bb337ae22fb6c00a46336230a51a926b3bd19939ffb2307 0.600000000000 1436329 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": 976346, "vin": [ { "gen": { "height": 976336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa33fc1bcc0fd0ec1bb337ae22fb6c00a46336230a51a926b3bd19939ffb2307" } } ], "extra": [ 1, 90, 210, 127, 174, 168, 250, 232, 127, 200, 34, 70, 242, 76, 161, 233, 122, 13, 149, 114, 133, 123, 6, 63, 9, 49, 64, 90, 122, 187, 75, 71, 139, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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