Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7b1dd04d1577458bb6938a31267cf2f16a82c6f8fdd1c9a4892cc0b4f355068

Tx prefix hash: 6ef7eff61fc2af58932c65053ca339dc78c88b0085f0b7911cd514ad74941ed3
Tx public key: c43b2d84d2762795907dd853f82580ef29eaebc09015af77c632d9fb6317e5ae
Timestamp: 1710333627 Timestamp [UCT]: 2024-03-13 12:40:27 Age [y:d:h:m:s]: 01:005:22:10:23
Block: 977438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265217 RingCT/type: yes/0
Extra: 01c43b2d84d2762795907dd853f82580ef29eaebc09015af77c632d9fb6317e5ae0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b70a62ab0f276c304fb9d3fb47b5a9962de0d2a4b15cebc1cb8f32765581c667 0.600000000000 1437441 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": 977448, "vin": [ { "gen": { "height": 977438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b70a62ab0f276c304fb9d3fb47b5a9962de0d2a4b15cebc1cb8f32765581c667" } } ], "extra": [ 1, 196, 59, 45, 132, 210, 118, 39, 149, 144, 125, 216, 83, 248, 37, 128, 239, 41, 234, 235, 192, 144, 21, 175, 119, 198, 50, 217, 251, 99, 23, 229, 174, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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