Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf805bf42962816a6f504c78f2ea015d5fee9ede78d379a462f41dbe65b58e10

Tx prefix hash: 901dfb2d051846960b0fc245089fe3620edb072e207c2a182e9980a62f04071b
Tx public key: e324814a10df3a201603fb125f15f68271c2c3f69f777bde748abf108dbd9824
Timestamp: 1725132731 Timestamp [UCT]: 2024-08-31 19:32:11 Age [y:d:h:m:s]: 01:060:10:15:05
Block: 1100105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301629 RingCT/type: yes/0
Extra: 01e324814a10df3a201603fb125f15f68271c2c3f69f777bde748abf108dbd9824021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3adcf1f13a3c66b086419854c55ed7f72061b82b0ce7b0f1223cbdfe6a64680b 0.600000000000 1576078 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": 1100115, "vin": [ { "gen": { "height": 1100105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3adcf1f13a3c66b086419854c55ed7f72061b82b0ce7b0f1223cbdfe6a64680b" } } ], "extra": [ 1, 227, 36, 129, 74, 16, 223, 58, 32, 22, 3, 251, 18, 95, 21, 246, 130, 113, 194, 195, 246, 159, 119, 123, 222, 116, 138, 191, 16, 141, 189, 152, 36, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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