Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bfb654fe2489ccefd3d2dba653ae4ee22fdb0304cc89410dc794c76a93d0b08

Tx prefix hash: ec72f9c89df5ef9ab65666975fe3516394f753635a4f7f378fad46051c956ab9
Tx public key: 969e2de859b075c19cfa775908e83661096f54e6d7aefb68c56f3e652ac189bc
Timestamp: 1636590475 Timestamp [UCT]: 2021-11-11 00:27:55 Age [y:d:h:m:s]: 03:171:11:06:46
Block: 371754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 900961 RingCT/type: yes/0
Extra: 01969e2de859b075c19cfa775908e83661096f54e6d7aefb68c56f3e652ac189bc02110000000ef56b629f000000000000000000

1 output(s) for total of 35.993581874000 dcy

stealth address amount amount idx
00: 9c1dc2a801e65867f9466be5d6b31e25290520ba9a76b746ef7d3e34a5f491f8 35.993581874000 753250 of 0

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": 371764, "vin": [ { "gen": { "height": 371754 } } ], "vout": [ { "amount": 35993581874, "target": { "key": "9c1dc2a801e65867f9466be5d6b31e25290520ba9a76b746ef7d3e34a5f491f8" } } ], "extra": [ 1, 150, 158, 45, 232, 89, 176, 117, 193, 156, 250, 119, 89, 8, 232, 54, 97, 9, 111, 84, 230, 215, 174, 251, 104, 197, 111, 62, 101, 42, 193, 137, 188, 2, 17, 0, 0, 0, 14, 245, 107, 98, 159, 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