Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eb7093ceb81f8ab184264ebac3de8be1e1df3c2baed83f3ce36a9b7d997d9d8

Tx prefix hash: f36a0b808bdcca1b8d18220e939cdf7a9b89158f0e07c236431db819bc1f1d7b
Tx public key: b0b229bb91ffa7ddfa08324c74580ad418ac0dc0fc670ae2db5646f5f2b63353
Timestamp: 1733459799 Timestamp [UCT]: 2024-12-06 04:36:39 Age [y:d:h:m:s]: 01:027:12:59:51
Block: 1169037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278148 RingCT/type: yes/0
Extra: 01b0b229bb91ffa7ddfa08324c74580ad418ac0dc0fc670ae2db5646f5f2b633530211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20724c3e05bd4fc61e63329ef2bc1121ed3daeb7cbdaa8077a89b10b8308af41 0.600000000000 1654750 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": 1169047, "vin": [ { "gen": { "height": 1169037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20724c3e05bd4fc61e63329ef2bc1121ed3daeb7cbdaa8077a89b10b8308af41" } } ], "extra": [ 1, 176, 178, 41, 187, 145, 255, 167, 221, 250, 8, 50, 76, 116, 88, 10, 212, 24, 172, 13, 192, 252, 103, 10, 226, 219, 86, 70, 245, 242, 182, 51, 83, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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