Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87d40cbd7f3d3a786904c36e841fd68edff13c955ed281e164db44cf528dea86

Tx prefix hash: f4f52a85f80a527abadd4b2299c6ff4d9a80ced9dcec89443a4440a44f51648b
Tx public key: 1ee446c7e3e0854e2195805c36561e4e2954a48a4d3b7b082a9963242824c659
Timestamp: 1706000032 Timestamp [UCT]: 2024-01-23 08:53:52 Age [y:d:h:m:s]: 01:082:20:54:54
Block: 941463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320328 RingCT/type: yes/0
Extra: 011ee446c7e3e0854e2195805c36561e4e2954a48a4d3b7b082a9963242824c65902110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b8079a31b5627282704baee409c3d1e36a5d0b6d73eb2d6aaadfeec09d2b10 0.600000000000 1399613 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": 941473, "vin": [ { "gen": { "height": 941463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b8079a31b5627282704baee409c3d1e36a5d0b6d73eb2d6aaadfeec09d2b10" } } ], "extra": [ 1, 30, 228, 70, 199, 227, 224, 133, 78, 33, 149, 128, 92, 54, 86, 30, 78, 41, 84, 164, 138, 77, 59, 123, 8, 42, 153, 99, 36, 40, 36, 198, 89, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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