Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25711dff2397654ffba176b91492005c2a1cb60a71aa1789f9e2aa12ca0ebf6

Tx prefix hash: c72c5e403a0f3ff638f6c3422f6e1b9254795648eb8923a03e97af6bdfac16ab
Tx public key: d3a5a81075f5a1cf05210e5a81d5987028e860e03f2255527568631163af68e8
Timestamp: 1610174911 Timestamp [UCT]: 2021-01-09 06:48:31 Age [y:d:h:m:s]: 03:358:07:17:54
Block: 176405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1011519 RingCT/type: yes/0
Extra: 01d3a5a81075f5a1cf05210e5a81d5987028e860e03f2255527568631163af68e8021100000090508974f9000000000000000000

1 output(s) for total of 159.779192861000 dcy

stealth address amount amount idx
00: 1352dc7af710cda9b043275a0e80db1225d845620b68eec58247e48c2fbaab13 159.779192861000 337887 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": 176415, "vin": [ { "gen": { "height": 176405 } } ], "vout": [ { "amount": 159779192861, "target": { "key": "1352dc7af710cda9b043275a0e80db1225d845620b68eec58247e48c2fbaab13" } } ], "extra": [ 1, 211, 165, 168, 16, 117, 245, 161, 207, 5, 33, 14, 90, 129, 213, 152, 112, 40, 232, 96, 224, 63, 34, 85, 82, 117, 104, 99, 17, 99, 175, 104, 232, 2, 17, 0, 0, 0, 144, 80, 137, 116, 249, 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