Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bdfb407c7b45ab5177250ca206ee614082638d5f963d6c9a66d0f1f7ad8ffa3

Tx prefix hash: f23521bee495d88a1e4b39967a0b6fcbcbb151db5d6dd4e4882618a88ab18796
Tx public key: 611581147e7b89b5b892f5224c1751afad345bb96e9d43b7a3b9792904f2f519
Timestamp: 1731230167 Timestamp [UCT]: 2024-11-10 09:16:07 Age [y:d:h:m:s]: 00:013:21:22:20
Block: 1150568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9938 RingCT/type: yes/0
Extra: 01611581147e7b89b5b892f5224c1751afad345bb96e9d43b7a3b9792904f2f5190211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d1a7bce32a85e2e0e921bdbcaa56ee1c15ab7261e4ad1ba0883278f69ea573f 0.600000000000 1635921 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": 1150578, "vin": [ { "gen": { "height": 1150568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d1a7bce32a85e2e0e921bdbcaa56ee1c15ab7261e4ad1ba0883278f69ea573f" } } ], "extra": [ 1, 97, 21, 129, 20, 126, 123, 137, 181, 184, 146, 245, 34, 76, 23, 81, 175, 173, 52, 91, 185, 110, 157, 67, 183, 163, 185, 121, 41, 4, 242, 245, 25, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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