Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1915d53274e4704e801eb9ef7e36f7db56146efda1fc90c9026582ede04435d0

Tx prefix hash: 3035f2713eb2ae0e30db15d006980cc23b2b566b8012b051e9898e6af807eaf9
Tx public key: d5e9ba30b6d68ceb6600588c4fbb938f55a4a8cdc0a950c5bffe388f88cbf10a
Timestamp: 1577806331 Timestamp [UCT]: 2019-12-31 15:32:11 Age [y:d:h:m:s]: 04:331:19:13:23
Block: 35863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126201 RingCT/type: yes/0
Extra: 01d5e9ba30b6d68ceb6600588c4fbb938f55a4a8cdc0a950c5bffe388f88cbf10a021100000026d81c26c0000000000000000000

1 output(s) for total of 466.855060669000 dcy

stealth address amount amount idx
00: 6f4613e391f76843eed25fe739655a4acfcf3d31e894059b1f18f28c13dd93f6 466.855060669000 60542 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": 35873, "vin": [ { "gen": { "height": 35863 } } ], "vout": [ { "amount": 466855060669, "target": { "key": "6f4613e391f76843eed25fe739655a4acfcf3d31e894059b1f18f28c13dd93f6" } } ], "extra": [ 1, 213, 233, 186, 48, 182, 214, 140, 235, 102, 0, 88, 140, 79, 187, 147, 143, 85, 164, 168, 205, 192, 169, 80, 197, 191, 254, 56, 143, 136, 203, 241, 10, 2, 17, 0, 0, 0, 38, 216, 28, 38, 192, 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