Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1276405cc12fd0e7bf24d1c37d748b029f0fb0637f9d3893417136c60625c0ce

Tx prefix hash: b5150d7edcb3db364a6e939365f68a78ab0af6a6d63f78b6e169eaa7e684ba53
Tx public key: 377202558bdf1c6ac9005d9745012e14c0b7a189467531a8e5a5f518c6ca7b11
Timestamp: 1725859577 Timestamp [UCT]: 2024-09-09 05:26:17 Age [y:d:h:m:s]: 00:120:05:49:36
Block: 1106139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85985 RingCT/type: yes/0
Extra: 01377202558bdf1c6ac9005d9745012e14c0b7a189467531a8e5a5f518c6ca7b1102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41c9136ce9b80231faa29a52bf95900774b5640783c5cfb2a3ac1ba4ee20008c 0.600000000000 1583726 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": 1106149, "vin": [ { "gen": { "height": 1106139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c9136ce9b80231faa29a52bf95900774b5640783c5cfb2a3ac1ba4ee20008c" } } ], "extra": [ 1, 55, 114, 2, 85, 139, 223, 28, 106, 201, 0, 93, 151, 69, 1, 46, 20, 192, 183, 161, 137, 70, 117, 49, 168, 229, 165, 245, 24, 198, 202, 123, 17, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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