Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4c8e34eb64e53d20e34f56fb8c7839b5f7b6ea8139f461132b20fafc7bf52f

Tx prefix hash: 679e965e31270e65c15f0f9b7592e1591c31a5950a12290cd34150fcf5138a47
Tx public key: f179f5406fe484a4a8420fcdb3b9f5c6ba50f1a1fc68a13c542e015c9f8939db
Timestamp: 1728704800 Timestamp [UCT]: 2024-10-12 03:46:40 Age [y:d:h:m:s]: 00:213:23:28:08
Block: 1129736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152728 RingCT/type: yes/0
Extra: 01f179f5406fe484a4a8420fcdb3b9f5c6ba50f1a1fc68a13c542e015c9f8939db021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 762191b78ac1074a4a02094fd606de41b378128376de13860b4f9b061a6964f5 0.600000000000 1612587 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": 1129746, "vin": [ { "gen": { "height": 1129736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "762191b78ac1074a4a02094fd606de41b378128376de13860b4f9b061a6964f5" } } ], "extra": [ 1, 241, 121, 245, 64, 111, 228, 132, 164, 168, 66, 15, 205, 179, 185, 245, 198, 186, 80, 241, 161, 252, 104, 161, 60, 84, 46, 1, 92, 159, 137, 57, 219, 2, 17, 0, 0, 0, 2, 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