Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5581800fc0b5bd138b85c22af27ee44c3f9e5e53eeedd2a3d1d0221c7192af4f

Tx prefix hash: 3a1664a7dc2438ea6e09ebf4e44a7242a71457f3c589f5fdb7dfb5aee1bdec1f
Tx public key: 5d27158d68ebde0381aa0e53ef2f0afb5abdd9c5fb76738a940603dd8cde43a0
Timestamp: 1672276290 Timestamp [UCT]: 2022-12-29 01:11:30 Age [y:d:h:m:s]: 02:098:20:27:06
Block: 662758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592353 RingCT/type: yes/0
Extra: 015d27158d68ebde0381aa0e53ef2f0afb5abdd9c5fb76738a940603dd8cde43a002110000000283600029000000000000000000

1 output(s) for total of 3.908477264000 dcy

stealth address amount amount idx
00: 50f2ea9a0fab51b0573233722695cd2ce5d856cdec34377cfb2271c9aa59d0f2 3.908477264000 1103625 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": 662768, "vin": [ { "gen": { "height": 662758 } } ], "vout": [ { "amount": 3908477264, "target": { "key": "50f2ea9a0fab51b0573233722695cd2ce5d856cdec34377cfb2271c9aa59d0f2" } } ], "extra": [ 1, 93, 39, 21, 141, 104, 235, 222, 3, 129, 170, 14, 83, 239, 47, 10, 251, 90, 189, 217, 197, 251, 118, 115, 138, 148, 6, 3, 221, 140, 222, 67, 160, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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